Asset Return Technology

ABSTRACT

One or more identifiers are received based on an electronic scan of computer-readable indicia. The computer-readable indicia being coupled to an asset. The asset is associated with one or more shipping operations. Based at least in part on the one or more identifiers, it is determined that the asset is requested for return. Based at least in part on the one or more identifiers, a shipping label corresponding to a destination location for the asset to be returned to is automatically generated or a location for the asset to be delivered to is automatically changed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 63/013,311 entitled “Improved Asset Return Technology,” filed Apr.21, 2020, which is incorporated by reference in its entirety.

BACKGROUND

Before an asset (e.g., a package or parcel) is returned by a consigneeor recipient, it may go through various operations. For instance, aftera user orders an item from an electronic commerce web application andinputs shipping information (e.g., the delivery destination address),the item may be placed in a package and routed to a sorting facilitywhere the package is organized based on information associated with thepackage (e.g., size of package, destination address, etc.). Aftertraversal of the package through the sorting facility, the package maybe loaded into a carrier vehicle for delivery to the recipient at thedelivery destination. However, the item may be damaged, the item may bethe wrong item, or the item may otherwise be unacceptable by therecipient. In some instances, the recipient may then manually open a webapplication to facilitate the return of the item back to the shippingentity.

Typical scanning device technologies, printer technologies, and assetreturn technologies in general (e.g., web applications and carriercomputers) include static components or are limited in functionality.Additionally, existing technologies consume an unnecessary amount ofcomputing resources, such as CPU and computer network resources. Asdescribed in more detail herein, aspects improve each these technologiesand computing resource consumption.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the detaileddescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used in isolation as an aid in determining the scope of the claimedsubject matter. Further, alternative or additional embodiments existother than those described in this summary section.

Some embodiments are directed to a computer-implemented method thatcomprises the following operations. At a first time, an indication thatcomputer-readable indicia is electronically scanned by a computingdevice is received. The computer-readable indicia is coupled to anasset. The asset is shipped by a shipping entity and delivered to adestination location associated with a recipient of the asset. At leastpartially in response to the receiving of the indication, it isdetermined that the asset is requested to be returned back to theshipping entity. Based at least in part on content of thecomputer-readable indicia, the destination location is automaticallychanged, in a structured data record stored in computer memory, to areturn location associated with the shipping entity.

Some embodiments are directed a system that includes one or moreprocessors and one or more computer storage media storingcomputer-useable instructions that, when used by the one or moreprocessors, causes the one or more processors to perform a method. Insome aspects, the method comprises the following operations. At a firsttime, one or more identifiers are received based on an electronic scanof computer-readable indicia. The computer-readable indicia beingcoupled to an asset. The asset is associated with one or more shippingoperations. Based at least in part on the one or more identifiers, it isdetermined that the asset is requested for return. Based at least inpart on the one or more identifiers, a shipping label corresponding to adestination location for the asset to be returned to is automaticallygenerated.

Some embodiments are directed to a computer storage media havingcomputer-executable instructions embodied thereon that, when executed,by a processor, causes the processor to perform a method. In someaspects, the method includes the following operations. A mobile deviceelectronically scans computer-readable indicia that is coupled to anasset. The asset is associated with one or more shipping operations. Atleast partially in response to the electronically scanning, the mobiledevice generates one or more portions of a user interface. The one ormore portions are indicative of a prompt for a user to inputverification information for a return of the asset. Based at least inpart on the generating of the one or more portions, the mobile devicegenerates a notification that includes a request to return the asset.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described the disclosure in general terms, reference willnow be made to the accompanying drawings, which are not necessarilydrawn to scale, and wherein:

FIG. 1 is a schematic diagram of an example computing environment inwhich aspects of the present disclosure are employed in, according tosome embodiments.

FIG. 2 is a schematic diagram of one or more logistics server(s) orthird party server(s) in which aspects of the present disclosure areemployed in, according to some embodiments.

FIG. 3 is a schematic diagram of a computing entity in which aspects ofthe present disclosure are employed in, according to some embodiments.

FIG. 4 is a block diagram of a system for generating a return shippinglabel, according to some embodiments.

FIG. 5 is a block diagram of a system for generating a return labelrequest and a notification, according to some embodiments.

FIG. 6 is a schematic diagram of an environment illustrating how anasset return request may be generated and what a shipping label may looklike, according to some embodiments.

FIG. 7 is a schematic diagram of an environment illustrating how anasset return request may be generated and an associated user interface,according to some embodiments.

FIG. 8 is a flow diagram of an example process for automaticallychanging a destination location for one or more assets to be deliveredto for the generating of a return label, according to some embodiments.

FIG. 9 is a flow diagram of an example process for generating one ormore notifications that include a request to return one or more assets,according to some embodiments.

DETAILED DESCRIPTION OF THE INVENTION

The present disclosure will now be described more fully hereinafter withreference to the accompanying drawings, in which some, but not allembodiments of the disclosure are shown. Indeed, the disclosure may beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein. Rather, these embodiments areprovided so that this disclosure will satisfy applicable legalrequirements. Like numbers refer to like elements throughout.

I. Overview

As described above, asset return technologies in general have limitedfunctionality. For instance, carrier computers, web applications, orapps are limited in their functionality. For example, if a recipientdesired to return an asset, the user may have to manually log onto a webapplication or app to manually input necessary information for thereturn request. These applications thus require tedious manual userinput to complete user requests to return items. Alternatively, therecipient may have to travel to a carrier store, stand in line, and waitfor carrier personnel to manually input return label information (e.g.,return address, reasons for return, etc.) on a carrier computer andmanually request a printing of a shipping label to return the asset tothe new return address. In other instances, the recipient may requestthat carrier personnel travel to the address of the recipient to pick upthe asset needing to be returned, after which carrier personnel may besubject to the same manual input and requests to generate a shippinglabel for the return of the asset on carrier computing entities, such asa Delivery Information Acquisition Device (DIAD). All of these manualcomputer user input actions may be arduous, time consuming,unnecessarily consume vehicle resources (e.g., fuel), and the like forboth carrier personnel and recipients.

Various embodiments of the present disclosure improve these asset returntechnologies because they include new functions (e.g., automatedfunctions) that no carrier computers or applications (or humans usingcomputers or applications) perform based on new rules. For example, inresponse to electronically scanning computer-readable indicia (a firstrule), embodiments automatically generate one or more portions of a userinterface to prompt a user to input verification information (e.g.,authentication credentials) for a return of the asset, which no carriercomputers, web applications or apps currently do. In another example,based at least in part on receiving an indication that computer-readableindicia is electronically scanned, it can be determined that a recipientof the asset has requested a return of the asset. Based at least in parton content of the computer-readable indicia, a location for the asset tobe delivered to can be automatically changed in a structured data recordstored in computer memory, which no carrier computers or applicationsperform. The computer-readable indicia may contain the new address(e.g., a return address), which may be used for the change.

In some embodiments, the computer-readable indicia (e.g., a QR code)that is scanned may include new information, such as an asset ID andaddress of the site to facilitate a return. This new information may beused to automatically change data of the location in the structured datarecord. Additionally, some embodiments improve these asset returntechnologies because they automatically generate a shipping label basedon the information in the computer-readable indicia or identifiersreceived from an electronic scan. The shipping label may contain the newaddress (e.g., a return address), which is included in thecomputer-readable indicia. In this way, users to not have to manuallyperform arduous computer inputs to request and facilitate the return ofassets using static functionality but can use the new dynamicfunctionality described herein to automate the return of assets, therebymaking returns less arduous, fuel-efficient, less time consuming, andthe like.

Typical scanning technologies also have limited functionality orcomponents. For example, typical scanning technologies, such as mobileapplication scanners (e.g., Quick Response (QR) scanners) illuminate acorresponding code so that a scanning device (e.g., a camera) can detectthe illuminated light, which is then decoded. The decoding is often usedfor particular but limited functionality, such as redirecting users towebsites. Some embodiments improve these scanning technologies via newfunctionality that scanning technologies do not currently employ. Forexample, some embodiments automatically change, in a structured datarecord, a location for an asset to be delivered to in response toreceiving an indication that computer-readable indicia is electronicallyscanned. This may be indicative of automatically changing an originaladdress destined for a recipient to an address corresponding to the siteof return of the asset. In some embodiments, the computer-readableindicia (e.g., a QR code) that is scanned may include new informationrelative to existing QR codes, such as an asset ID and address of thesite to facilitate a return. This information may be used toautomatically change the location in the structured data record.Additionally, some embodiments improve these scanning technologiesbecause they automatically generate a shipping label based on one ormore new rules, such as the information in the computer-readable indiciaor identifiers received from an electronic scan, which no scanningtechnologies do. The shipping label may contain the new address (areturn address), which is included in the computer-readable indicia.

Other technologies, such as printer machines are also static and includelimited functionality. For example, users, such as carrier personnel,may have to manually input information on a digital shipping label(e.g., destination address, date, service class, size of package, etc.).Users may then have to manually request a print of the label via anoperating system on a carrier computer before the label is printed andbefore the user places the label on the package. Various embodiments ofthe present disclosure improve these printer machine technologiesbecause they automate new functions that these printers (and humansusing printers) have not performed before via one or more new rules. Forexample, no existing printer machines automatically generate or print aprinting label based on automatically changing, in a structured datarecord, a location for the asset to be delivered to or based on thecontents of the machine-readable indicia (e.g., which includes anaddress of the site of return of the asset).

As described above, existing technologies consume an unnecessaryquantity of computing resources. For example, existing technologiescause CPU bottlenecks, decrease in throughput, or network bandwidthissues, among other things. This is because when a user requests areturn, for example, carrier computers (e.g., at carrier stores) may beprocessing and printing multiple return requests at a single time ornear the same time for customers waiting in line. Some embodimentsimprove this computing resource consumption because the return requestsare largely shifted to recipients and recipient devices. For example, auser can use her mobile device to scan machine-readable indicia locatedon an asset, which automatically triggers a change of a destinationlocation (shipping address is now return address) and/or automaticallytriggers a shipping label to be printed. In another example, userdevices can be used to directly print shipping labels instead of carriercomputers. In this way, carrier computers do not solely bear the burdenfor processing various return requests at substantially the same time.Rather, recipient users can help crowdsource returns, thereby allowingmore data to be processed per unit of time to increase networkbandwidth, throughput, and CPU functioning of carrier computers, amongother things.

In is understood that although this overview section describes variousimprovements to conventional solutions and technologies, these are byway of example only. As such, other improvements are described below orwill become evident through description of various embodiments. Thisoverview is provided to introduce a selection of concepts in asimplified form that are further described below in the detaileddescription. This overview is not intended to: identify key features oressential features of the claimed subject matter, key improvements, noris it intended to be used in isolation as an aid in determining thescope of the claimed subject matter.

II. Apparatuses, Methods, and Systems

Embodiments of the present disclosure may be implemented in variousways, including as apparatuses that comprise articles of manufacture. Anapparatus may include a non-transitory computer-readable storage mediumstoring applications, programs, program modules, scripts, source code,program code, object code, byte code, compiled code, interpreted code,machine code, executable instructions, and/or the like (also referred toherein as executable instructions, instructions for execution, programcode, and/or similar terms used herein interchangeably). Suchnon-transitory computer-readable storage media include allcomputer-readable media (including volatile and non-volatile media).

In one embodiment, a non-volatile computer-readable storage medium mayinclude a floppy disk, flexible disk, hard disk, solid-state storage(SSS) (e.g., a solid state drive (SSD), solid state card (SSC), solidstate module (SSM)), enterprise flash drive, magnetic tape, or any othernon-transitory magnetic medium, and/or the like. A non-volatilecomputer-readable storage medium may also include a punch card, papertape, optical mark sheet (or any other physical medium with patterns ofholes or other optically recognizable indicia), compact disc read onlymemory (CD-ROM), compact disc-rewritable (CD-RW), digital versatile disc(DVD), Blu-ray disc (BD), any other non-transitory optical medium,and/or the like. Such a non-volatile computer-readable storage mediummay also include read-only memory (ROM), programmable read-only memory(PROM), erasable programmable read-only memory (EPROM), electricallyerasable programmable read-only memory (EEPROM), flash memory (e.g.,Serial, NAND, NOR, and/or the like), multimedia memory cards (MMC),secure digital (SD) memory cards, SmartMedia cards, CompactFlash (CF)cards, Memory Sticks, and/or the like. Further, a non-volatilecomputer-readable storage medium may also include conductive-bridgingrandom access memory (CBRAM), phase-change random access memory (PRAM),ferroelectric random-access memory (FeRAM), non-volatile random-accessmemory (NVRAM), magnetoresistive random-access memory (MRAM), resistiverandom-access memory (RRAM), Silicon-Oxide-Nitride-Oxide-Silicon memory(SONOS), floating junction gate random access memory (FJG RAM),Millipede memory, racetrack memory, and/or the like.

In one embodiment, a volatile computer-readable storage medium mayinclude random access memory (RAM), dynamic random access memory (DRAM),static random access memory (SRAM), fast page mode dynamic random accessmemory (FPM DRAM), extended data-out dynamic random access memory (EDODRAM), synchronous dynamic random access memory (SDRAM), doubleinformation/data rate synchronous dynamic random access memory (DDRSDRAM), double information/data rate type two synchronous dynamic randomaccess memory (DDR2 SDRAM), double information/data rate type threesynchronous dynamic random access memory (DDR3 SDRAM), Rambus dynamicrandom access memory (RDRAM), Twin Transistor RAM (TTRAM), Thyristor RAM(T-RAM), Zero-capacitor (Z-RAM), Rambus in-line memory module (RIMM),dual in-line memory module (DIMM), single in-line memory module (SIMM),video random access memory (VRAM), cache memory (including variouslevels), flash memory, register memory, and/or the like. It will beappreciated that where embodiments are described to use acomputer-readable storage medium, other types of computer-readablestorage media may be substituted for or used in addition to thecomputer-readable storage media described above.

As should be appreciated, various embodiments of the present disclosuremay also be implemented as methods, apparatus, systems, computingdevices/entities, computing entities, and/or the like. As such,embodiments of the present disclosure may take the form of an apparatus,system, computing device, computing entity, and/or the like executinginstructions stored on a computer-readable storage medium to performcertain steps or operations. However, embodiments of the presentdisclosure may also take the form of an entirely hardware embodimentperforming certain steps or operations.

Embodiments of the present disclosure are described below with referenceto block diagrams and flowchart illustrations. Thus, it should beunderstood that each block of the block diagrams and flowchartillustrations may be implemented in the form of a computer programproduct, an entirely hardware embodiment, a combination of hardware andcomputer program products, and/or apparatus, systems, computingdevices/entities, computing entities, and/or the like carrying outinstructions, operations, steps, and similar words used interchangeably(e.g., the executable instructions, instructions for execution, programcode, and/or the like) on a computer-readable storage medium forexecution. For example, retrieval, loading, and execution of code may beperformed sequentially such that one instruction is retrieved, loaded,and executed at a time. In some exemplary embodiments, retrieval,loading, and/or execution may be performed in parallel such thatmultiple instructions are retrieved, loaded, and/or executed together.Thus, such embodiments can produce specifically-configured machinesperforming the steps or operations specified in the block diagrams andflowchart illustrations. Accordingly, the block diagrams and flowchartillustrations support various combinations of embodiments for performingthe specified instructions, operations, or steps.

III. Exemplary System Architecture

FIG. 1 is a schematic diagram of an example computing environment 100 inwhich aspects of the present disclosure are employed in, according tosome embodiments. As shown in FIG. 1, this particular computingenvironment 100 includes one or more logistics servers 105 (e.g., ashipping company mainframe, a blade server, cloud computing nodes, orlogistics store desktop) one or more third party servers 125 (e.g., anelectronic commerce entity that hosts a marketplace web application)computing entities 110 (e.g., a mobile device, such as a DIAD or mobilephone), and one or more printers 123 (e.g., to print a shipping label),which are communicatively coupled via one or more networks 135. In someembodiments, “communicatively coupled” means that two or more componentscan perform data transportation between each other via a wired (e.g.,ethernet or fiber-optic medium connected in a LAN) or wireless (e.g.,IEEE 802.15.4) computer protocol network. Each of these components,entities, devices, systems, and similar words used hereininterchangeably may be in direct or indirect communication with, forexample, one another over the same or different wired and/or wirelessnetworks. Additionally, while FIG. 1 illustrates the various systementities as separate, standalone entities, the various embodiments arenot limited to this particular architecture. In some embodiments, thereare more or fewer (or combined) components than illustrated in theenvironment 100. For example, there need not be a third party server 125and/or a printer 123.

In various embodiments, the network(s) 135 represents or includes an IoT(internet of things) or IoE (internet of everything) network, which is anetwork of interconnected items (e.g., the printer(s) 123 and the mobilecomputing entity 110) that are each provided with unique identifiers(e.g., UIDs) and computing logic so as to communicate or transfer datawith each other or other components. Such communication can happenwithout requiring human-to-human or human-to-computer interaction. Forexample, an IoT network may include the mobile computing entity 110 ofan asset recipient, which is equipped with one or more sensors andtransmitter in order to process and/or transmit data (e.g., a controlsignal) over the network 135 to the logistics server(s) 105, theprinter(S) 123, and/or the third party server(s) 125. In the context ofan IoT network, a computing device can be or include one or more localprocessing devices (e.g., edge nodes) that are one or more computingdevices configured to store and process, over the network(s) 135, eithera subset or all of the received or respective sets of data to the one ormore remote computing devices (e.g., the computing entities 110 and/orthe logistics server(s) 105) for analysis.

In some embodiments, the local processing device(s) described above is amesh or other network of microdata centers or edge nodes that processand store local data received from the mobile computing entity 110, thelogistics server(s) 105, the third party server(s) 125, and/or theprinter(s) 123 and push or transmit some or all of the data to a clouddevice or a corporate data center that is or is included in the one ormore logistics server(s) 105. In some embodiments, the local processingdevice(s) store all of the data and only transmit selected (e.g., datathat meets a threshold) or important data to the one or more logisticsservers 105. Accordingly, the non-important data or the data that is ina group that does not meet a threshold is not transmitted. In variousembodiments where the threshold or condition is not met, daily or othertime period reports are periodically generated and transmitted from thelocal processing device(s) to the remote device(s) indicating all thedata readings gathered and processed at the local processing device(s).In some embodiments, the one or more local processing devices act as abuffer or gateway between the network(s) and a broader network, such asthe one or more networks 135. Accordingly, in these embodiments, the oneor more local processing devices can be associated with one or moregateway devices that translate proprietary communication protocols intoother protocols, such as internet protocols.

In some embodiments, the computing environment 100 represents a networkof components that work together to facilitate the return of one or moreassets. For example, in response to a mobile computing entity 110 (e.g.,of an asset recipient) scanning computer-readable indicia located on apackage, the mobile computing entity may communicate, via the network135, with the logistics server(s) 105, which automatically causes a datarecord (e.g., of a database table) to be changed or more specifically,the address that the asset should be delivered to (e.g., based on afacility return address indicated in the computer-readable indicia).Additionally or alternatively, the communication, via the network 135,to the logistics server(s) 105 may cause the printer(s) 123 to print areturn shipping label for the asset return request. For example, thelogistics server(s) 105 may automatically send a control signal to theprinter(s) 123, thereby causing the return label to be physicallyprinted based on information indicated in the computer-readable indiciaand the scan of the computer-readable indicia. Additionally oralternatively, the computing entity 110 may send one or morenotifications (or control signals) that indicate the return request. Forexample, the computing entity 110 can transmit, via the network 110, anotification to the third party server(s) 125, which may be indicativeof a request to an electronic commerce entity to return an item, whichmay facilitate other actions, such as reimbursement, pickup of the itemrequested for return, and the like. Alternatively or additionally, asimilar notification can be transmitted to another computing entity 110,such as a shipper's mobile phone indicating that the recipient orconsignee is requesting a return of the shipped asset.

1. Exemplary Analysis Computing Entities

FIG. 2 provides a schematic of a logistics server(s) 105 and/or thethird party server(s) 125, according to particular embodiments of thepresent disclosure. In general, the terms computing entity, computer,entity, device, system, and/or similar words used herein interchangeablymay refer to, for example, one or more computers, computing entities,desktops, mobile phones, tablets, phablets, notebooks, laptops,distributed systems, consoles input terminals, servers or servernetworks, blades, gateways, switches, processing devices, processingentities, set-top boxes, relays, routers, network access points, basestations, cloud computing nodes, virtual machines, virtual containers,the like, and/or any combination of devices or entities adapted toperform the functions, operations, and/or processes described herein.Such functions, operations, and/or processes may include, for example,transmitting, receiving, operating on, processing, displaying, storing,determining, creating/generating, monitoring, evaluating, comparing,and/or similar terms used herein interchangeably. In particularembodiments, these functions, operations, and/or processes can beperformed on data, content, information/data, and/or similar terms usedherein interchangeably.

As indicated, in particular embodiments, the logistics server(s) 105and/or the third party server(s) 125 may also include one or morecommunications interfaces 220 for communicating with various computingentities, such as by communicating data, content, information/data,and/or similar terms used herein interchangeably that can betransmitted, received, operated on, processed, displayed, stored, and/orthe like.

As shown in FIG. 2, in particular embodiments, the logistics server(s)105 and/or the third party server(s) 125 may include or be incommunication with one or more processing elements 205 (also referred toas processors, processing circuitry, and/or similar terms used hereininterchangeably) that communicate with other elements within thelogistics server(s) 105 via a bus, for example. As will be understood,the processing element 205 may be embodied in a number of differentways. For example, the processing element 205 may be embodied as one ormore complex programmable logic devices (CPLDs), microprocessors,multi-core processors, co-processing entities, application-specificinstruction-set processors (ASIPs), microcontrollers, and/orcontrollers. Further, the processing element 205 may be embodied as oneor more other processing devices or circuitry. The term circuitry mayrefer to an entirely hardware embodiment or a combination of hardwareand computer program products. Thus, the processing element 205 may beembodied as integrated circuits, application specific integratedcircuits (ASICs), field programmable gate arrays (FPGAs), programmablelogic arrays (PLAs), hardware accelerators, other circuitry, and/or thelike. As will therefore be understood, the processing element 205 may beconfigured for a particular use or configured to execute instructionsstored in volatile or non-volatile media or otherwise accessible to theprocessing element 205. As such, whether configured by hardware orcomputer program products, or by a combination thereof, the processingelement 205 may be capable of performing steps or operations accordingto embodiments of the present disclosure when configured accordingly.

In particular embodiments, the logistics server(s) 105 and/or the thirdparty server(s) 125 may further include or be in communication withnon-volatile media (also referred to as non-volatile storage, memory,memory storage, memory circuitry and/or similar terms used hereininterchangeably). In particular embodiments, the non-volatile storage ormemory may include one or more non-volatile storage or memory media 210,including but not limited to hard disks, ROM, PROM, EPROM, EEPROM, flashmemory, MMCs, SD memory cards, Memory Sticks, CBRAM, PRAM, FeRAM, NVRAM,MRAM, RRAM, SONOS, FJG RAM, Millipede memory, racetrack memory, and/orthe like. As will be recognized, the non-volatile storage or memorymedia may store databases (e.g., parcel/item/shipment database),database instances, database management systems, data, applications,programs, program modules, scripts, source code, object code, byte code,compiled code, interpreted code, machine code, executable instructions,and/or the like. The term database, database instance, databasemanagement system, and/or similar terms used herein interchangeably mayrefer to a collection of records or information/data that is stored in acomputer-readable storage medium using one or more database models, suchas a hierarchical database model, network model, relational model,entity—relationship model, object model, document model, semantic model,graph model, and/or the like.

In particular embodiments, the logistics server(s) 105 and/or the thirdparty server(s) 125 may further include or be in communication withvolatile media (also referred to as volatile storage, memory, memorystorage, memory circuitry and/or similar terms used hereininterchangeably). In particular embodiments, the volatile storage ormemory may also include one or more volatile storage or memory media215, including but not limited to RAM, DRAM, SRAM, FPM DRAM, EDO DRAM,SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, TTRAM, T-RAM, Z-RAM,RIMM, DIMM, SIMM, VRAM, cache memory, register memory, and/or the like.As will be recognized, the volatile storage or memory media may be usedto store at least portions of the databases, database instances,database management systems, data, applications, programs, programmodules, scripts, source code, object code, byte code, compiled code,interpreted code, machine code, executable instructions, and/or the likebeing executed by, for example, the processing element 205. Thus, thedatabases, database instances, database management systems, data,applications, programs, program modules, scripts, source code, objectcode, byte code, compiled code, interpreted code, machine code,executable instructions, and/or the like may be used to control certainaspects of the operation of the logistics server(s) 105 with theassistance of the processing element 205 and operating system.

As indicated, in particular embodiments, the logistics server(s) 105and/or third party server(s) 125 may also include one or morecommunications interfaces 220 for communicating with various computingentities, such as by communicating information/data, content,information/data, and/or similar terms used herein interchangeably thatcan be transmitted, received, operated on, processed, displayed, stored,and/or the like. Such communication may be executed using a wiredinformation/data transmission protocol, such as fiber distributedinformation/data interface (FDDI), digital subscriber line (DSL),Ethernet, asynchronous transfer mode (ATM), frame relay,information/data over cable service interface specification (DOCSIS), orany other wired transmission protocol. Similarly, the logisticsserver(s) 105 may be configured to communicate via wireless externalcommunication networks using any of a variety of protocols, such asgeneral packet radio service (GPRS), Universal Mobile TelecommunicationsSystem (UMTS), Code Division Multiple Access 2000 (CDMA2000), CDMA20001X (1×RTT), Wideband Code Division Multiple Access (WCDMA), TimeDivision-Synchronous Code Division Multiple Access (TD-SCDMA), Long TermEvolution (LTE), Evolved Universal Terrestrial Radio Access Network(E-UTRAN), Evolution-Data Optimized (EVDO), High Speed Packet Access(HSPA), High-Speed Downlink Packet Access (HSDPA), IEEE 802.11 (Wi-Fi),Wi-Fi Direct, 802.16 (WiMAX), ultra wideband (UWB), infrared (IR)protocols, near field communication (NFC) protocols, Wibree, Bluetoothprotocols, wireless universal serial bus (USB) protocols, long range lowpower (LoRa), LTE Cat M1, NarrowBand IoT (NB IoT), and/or any otherwireless protocol.

Although not shown, the logistics server(s) 105 and/or third partyserver(s) 125 may include or be in communication with one or more inputelements, such as a keyboard input, a mouse input, a touchscreen/display input, motion input, movement input, audio input,pointing device input, joystick input, keypad input, and/or the like.The logistics server(s) 105 may also include or be in communication withone or more output elements (not shown), such as audio output, videooutput, screen/display output, motion output, movement output, and/orthe like.

As will be appreciated, one or more of the logistics server(s)'s 105and/or third party server(s) 125 components may be located remotely,such as in a distributed system (e.g., a cloud computing system).Additionally or alternatively, the logistics server(s) 105 and/or thethird party server(s) 125 may be represented among a plurality ofcomputing devices. For example, the logistics server(s) 105 and/or thethird party server(s) 125 can be or be included in a cloud computingenvironment, which includes a network-based, distributed/data processingsystem that provides one or more cloud computing services. Further, acloud computing environment can include many computers, hundreds orthousands of them or more, disposed within one or more data centers andconfigured to share resources over the network(s) 135. Furthermore, oneor more of the components may be combined and additional componentsperforming functions described herein may be included in the logisticsserver(s) 105 and/or the third party server(s) 125 Thus, the logisticsserver(s) 105 and/or third party server(s) 123 can be adapted toaccommodate a variety of needs and circumstances. As will be recognized,these architectures and descriptions are provided for exemplary purposesonly and are not limiting to the various embodiments.

2. Exemplary Computing Entities

Computing entities 110 may be configured for electronically scanningcomputer-readable indicia, sending notifications, receivingnotifications, and/or providing one or more portions of a userinterface, among other things In some embodiments, a computing entity110 is embedded within or otherwise coupled to the printer(s) 123 tofacilitate the printing of shipping labels. In certain embodiments,computing entities 110 may be embodied as handheld computing entities,such as mobile phones, tablets, personal digital assistants, and/or thelike, that may be operated at least in part based on user input receivedfrom a user via an input mechanism. Moreover, computing entities 110 maybe embodied as onboard vehicle computing entities, such as centralvehicle electronic control units (ECUs), onboard multimedia system,and/or the like that may be operated at least in part based on userinput. Such onboard vehicle computing entities may be configured forautonomous and/or nearly autonomous operation however, as they may beembodied as onboard control systems for autonomous or semi-autonomousvehicles, such as unmanned aerial vehicles (UAVs), robots, and/or thelike. As a specific example, computing entities 110 may be utilized asonboard controllers for UAVs configured for picking-up and/or deliveringpackages to various locations, and accordingly such computing entities110 may be configured to monitor various inputs (e.g., from varioussensors) and generated various outputs. It should be understood thatvarious embodiments of the present disclosure may comprise a pluralityof computing entities 110 embodied in one or more forms (e.g., parcelsecurity devices kiosks, mobile devices, watches, laptops, carrierpersonnel devices (e.g., Delivery Information Acquisition Devices(DIAD)), etc.)

As will be recognized, a user may be an individual, a family, a company,an organization, an entity, a department within an organization, arepresentative of an organization and/or person, and/or the like—whetheror not associated with a carrier. In particular embodiments, a user mayoperate a computing entity 110 that may include one or more componentsthat are functionally similar to those of the logistics server(s) 105.FIG. 3 provides an illustrative schematic representative of a computingentity 110 that can be used in conjunction with embodiments of thepresent disclosure. In general, the terms device, system, computingentity, entity, and/or similar words used herein interchangeably mayrefer to, for example, one or more: computers, computing entities,desktops, mobile phones, micro-computers (e.g., RASBERY PI), tablets,phablets, notebooks, laptops, distributed systems, vehicle multimediasystems, autonomous vehicle onboard control systems, watches, glasses,key fobs, radio frequency identification (RFID) tags/readers, earpieces, scanners, imaging devices/cameras (e.g., part of a multi-viewimage capture system), wristbands, kiosks, input terminals, servers orserver networks, blades, gateways, switches, processing devices,processing entities, set-top boxes, relays, routers, network accesspoints, base stations, the like, and/or any combination of devices orentities adapted to perform the functions, operations, and/or processesdescribed herein. Computing entities 110 can be operated by variousparties, including carrier personnel (sorters, loaders, deliverydrivers, network administrators, and/or the like). As shown in FIG. 3,the computing entity 110 can include an antenna 312, a transmitter 304(e.g., radio), a receiver 306 (e.g., radio), and a processing element308 (e.g., CPLDs, microprocessors, multi-core processors, coproces singentities, ASIPs, microcontrollers, and/or controllers) that providessignals to and receives signals from the transmitter 304 and receiver306, respectively. In some embodiments, the computing entity 110includes one or more sensors 330 (e.g., a camera with object detectioncapabilities). The one or more sensors 330 can be one or more of: apressure sensor, an accelerometer, a gyroscope, a geolocation sensor(e.g., GPS sensor), a radar, a lidar, sonar, ultrasound, an objectrecognition camera, and any other suitable sensor used to helpfacilitate the return of an asset.

The signals provided to and received from the transmitter 304 and thereceiver 306, respectively, may include signaling information inaccordance with air interface standards of applicable wireless systems.In this regard, the computing entity 110 may be capable of operatingwith one or more air interface standards, communication protocols,modulation types, and access types. More particularly, the computingentity 110 may operate in accordance with any of a number of wirelesscommunication standards and protocols, such as those described abovewith regard to the logistics server(s) 105. In a particular embodiment,the computing entity 110 may operate in accordance with multiplewireless communication standards and protocols, such as UMTS, CDMA2000,1×RTT, WCDMA, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, Wi-FiDirect, WiMAX, UWB, IR, NFC, Bluetooth, USB, and/or the like. Similarly,the computing entity 110 may operate in accordance with multiple wiredcommunication standards and protocols, such as those described abovewith regard to the logistics server(s) 105 via a network interface 320.

Via these communication standards and protocols, the computing entity110 can communicate with various other entities using concepts such asUnstructured Supplementary Service information/data (USSD), ShortMessage Service (SMS), Multimedia Messaging Service (MMS), Dual-ToneMulti-Frequency Signaling (DTMF), and/or Subscriber Identity ModuleDialer (SIM dialer). The computing entity 110 can also download changes,add-ons, and updates, for instance, to its firmware, software (e.g.,including executable instructions, applications, program modules), andoperating system.

According to particular embodiments, the computing entity 110 mayinclude location determining aspects, devices, modules, functionalities,and/or similar words used herein interchangeably. For example, thecomputing entity 110 may include outdoor positioning aspects, such as alocation module adapted to acquire, for example, latitude, longitude,altitude, geocode, course, direction, heading, speed, universal time(UTC), date, and/or various other information/data. In particularembodiments, the location module can acquire information/data, sometimesknown as ephemeris information/data, by identifying the number ofsatellites in view and the relative positions of those satellites (e.g.,using global positioning systems (GPS)). The satellites may be a varietyof different satellites, including Low Earth Orbit (LEO) satellitesystems, Department of Defense (DOD) satellite systems, the EuropeanUnion Galileo positioning systems, the Chinese Compass navigationsystems, Indian Regional Navigational satellite systems, and/or thelike. This information/data can be collected using a variety ofcoordinate systems, such as the Decimal Degrees (DD); Degrees, Minutes,Seconds (DMS); Universal Transverse Mercator (UTM); Universal PolarStereographic (UPS) coordinate systems; and/or the like. Alternatively,the location information can be determined by triangulating thecomputing entity's 110 position in connection with a variety of othersystems, including cellular towers, Wi-Fi access points, and/or thelike. Similarly, the computing entity 110 may include indoor positioningaspects, such as a location module adapted to acquire, for example,latitude, longitude, altitude, geocode, course, direction, heading,speed, time, date, and/or various other information/data. Some of theindoor systems may use various position or location technologiesincluding RFID tags, indoor beacons or transmitters, Wi-Fi accesspoints, cellular towers, nearby computing devices/entities (e.g.,smartphones, laptops) and/or the like. For instance, such technologiesmay include the iBeacons, Gimbal proximity beacons, Bluetooth Low Energy(BLE) transmitters, NFC transmitters, and/or the like. These indoorpositioning aspects can be used in a variety of settings to determinethe location of someone or something to within inches or centimeters.

The computing entity 110 may also comprise a user interface (that caninclude a display 316 coupled to a processing element 308) and/or a userinput interface (coupled to a processing element 308). For example, theuser interface may be a user application, browser, user interface,and/or similar words used herein interchangeably executing on and/oraccessible via the computing entity 110 to interact with and/or causedisplay of information from the logistics server(s) 105 and/or thirdparty server(s) 125, as described herein. The user input interface cancomprise any of a number of devices or interfaces allowing the computingentity 110 to receive information/data, such as a keypad 318 (hard orsoft), a touch display, voice/speech or motion interfaces, or otherinput device. In embodiments including a keypad 318, the keypad 318 caninclude (or cause display of) the conventional numeric (0-9) and relatedkeys (#, *), and other keys used for operating the computing entity 110and may include a full set of alphabetic keys or set of keys that may beactivated to provide a full set of alphanumeric keys. In addition toproviding input, the user input interface can be used, for example, toactivate or deactivate certain functions, such as screen savers and/orsleep modes.

As shown in FIG. 3, the computing entity 110 may also include an camera,imaging device, and/or similar words used herein interchangeably 326(e.g., still-image camera, video camera, IoT enabled camera, IoT modulewith a low resolution camera, a wireless enabled MCU, and/or the like)configured to capture images. The computing entity 110 may be configuredto capture images via the onboard camera 326, and to store those imagingdevices/cameras locally, such as in the volatile memory 322 and/ornon-volatile memory 324. As discussed herein, the computing entity 110may be further configured to match the captured image data with relevantlocation and/or time information captured via the location determiningaspects to provide contextual information/data, such as a time-stamp,date-stamp, location-stamp, and/or the like to the image data reflectiveof the time, date, and/or location at which the image data was capturedvia the camera 326. The contextual data may be stored as a portion ofthe image (such that a visual representation of the image data includesthe contextual data) and/or may be stored as metadata (e.g., data thatdescribes other data, such as describing a payload) associated with theimage data that may be accessible to various computing entities 110.

The computing entity 110 may include other input mechanisms, such asscanners (e.g., barcode scanners), microphones, accelerometers, RFIDreaders (or Near-Field Communication (NFC) readers), and/or the likeconfigured to capture and store various information types for thecomputing entity 110. For example, a scanner may be used to captureparcel/item/shipment information/data from an item indicator disposed ona surface of a shipment or other item. In certain embodiments, thecomputing entity 110 may be configured to associate any captured inputinformation/data, for example, via the onboard processing element 308.For example, scan data captured via a scanner may be associated withimage data captured via the camera 326 such that the scan data isprovided as contextual data associated with the image data.

The computing entity 110 can also include volatile storage or memory 322and/or non-volatile storage or memory 324, which can be embedded and/ormay be removable. For example, the non-volatile memory may be ROM, PROM,EPROM, EEPROM, flash memory, MMCs, SD memory cards, Memory Sticks,CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM, Millipede memory,racetrack memory, and/or the like. The volatile memory may be RAM, DRAM,SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM,RDRAM, TTRAM, T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM, cache memory,register memory, and/or the like. The volatile and non-volatile storageor memory can store databases, database instances, database managementsystems, information/data, applications, programs, program modules,scripts, source code, object code, byte code, compiled code, interpretedcode, machine code, executable instructions, and/or the like toimplement the functions of the computing entity 110. As indicated, thismay include a user application that is resident on the entity oraccessible through a browser or other user interface for communicatingwith the logistics server(s) 105 and/or various other computingentities.

In another embodiment, the computing entity 110 may include one or morecomponents or functionality that are the same or similar to those of thelogistics server(s) 105, as described in greater detail above. As willbe recognized, these architectures and descriptions are provided forexemplary purposes only and are not limiting to the various embodiments.

FIG. 4 is a block diagram of a system 400 for generating a returnshipping label, according to some embodiments. Although the system 400includes specific modules or components that operate in a particularorder, it is understood that this is representative only. As such, theremay be more or fewer components than illustrated, components may becombined, and/or functionality can be performed in a different orderthan illustrated. For example, in some embodiments, a physical returnlabel 409 is not printed or there is no label that is generated via thereturn label generator 407. In some embodiments, each of the componentsof the system 400 are located within the logistics server(s) 105.Alternatively, in some embodiments, the components of the system 400 arelocated within a different entity (e.g., computing entity 110) and/orare distributed among one or more components of the environment 100.

The registration module 401 is generally responsible for registering oneor more shippers and/or recipients of an asset. A “recipient” of anasset as described herein is a consignee (and not a consignor) of theasset, a buyer of the asset, and/or any other suitable person or entitythat receives an asset. In various embodiments, the receiving of theasset can occur at the final delivery destination (known as “last miledelivery”) (e.g., a recipient's home address) or other location, such asa locker bank, retailer store, access point, and/or the like.Registering may include receiving and storing user input of data, suchas shipper name, designated asset recipient(s) name, shipper mobilephone number, recipient mobile phone number, shipper address, devicedata (e.g. model and OS) of shipper and/or recipient, recipient address(corresponding to the delivery location), credit card information ofshipper, authentication credentials of shipper/recipient, particulardelivery request data (e.g., specific shipment attributes, such as aspecific shipment request at a particular delivery address), the addressor location of the carrier store facility that the recipient will dropthe asset off at should the recipient request a return of the asset,and/or any other suitable data needed to process a shipment and/or areturn of assets for shipments. All of this data can be stored to theuser profile data store 411 (e.g., a database).

The asset return request module 403 is generally responsible forreceiving an asset return request of a recipient to initiate the processof returning one or more assets. The asset return request module 403 canbe automatically triggered or be triggered via manual user input. Forexample, in some embodiments, a recipient of an asset may determine thathe or she wants to return an item because it is broken or is the wrongitem. Responsively, the recipient, holding his or her mobile device, canopen up an electronic scanning reader application locally stored to themobile device. Responsively, a camera device within the mobile devicemay activate. The recipient may then hold the camera device near (e.g.,within a distance and viewing threshold) computer-readable indicialocated on an asset such that the camera device captures and decodes thecomputer-readable indicia. In response to the camera device or otherelectronic scanning device of the mobile device electronically scanningthe computer-readable indicia, the mobile device may automatically senda request (e.g., over the network 135) to the logistics server(s) 105,which is received by the asset return request module 403. The requestmay be indicative of a request to return an item.

In some embodiments, the request described above to return one or moreitems includes metadata, such as device fingerprint of the recipient'sdevice (e.g., model, OS, etc.), recipient's mobile phone number, therecipient's IP address, and the like. The verification module 405 inparticular embodiments uses the metadata within the request and therequest itself to verify the recipient based on data located in the userprofile data store 411. For example, the request to return an item mayinclude metadata of the mobile device phone number of the mobile devicethat scanned the computer-readable indicia. This data may be matched todata within the user profile data store 411 (e.g., registered mobiledevice phone numbers, device fingerprints, recipient name, and the like)to authenticate the recipient and/or determine that the recipient isauthorized to return an item.

In some embodiments, the verification module 405 includes authenticationand authorization back-end functionality that is to be provided to auser interface of a web application or app and analyzed in response touser input. For example, in response to a mobile device associated witha recipient scanning machine-readable indicia, the mobile device maydisplay a web or app page that prompts the recipient to input his or hername, authentication information (e.g., password), shipper, etc. Inresponse to receiving an indication that the user has input thisinformation, the mobile device may transmit this information to thelogistics server(s) 105, which is then received by the verificationmodule 405 and compared against the data in the user profile data store411 in order to authenticate and authorize the recipient or therecipient's mobile device.

In some embodiments, in response to the verification module 405verifying the recipient, the return label generator 407 automaticallygenerates a return shipping label. In some embodiments, the return labelgenerator 407 additionally or alternatively changes, in a structureddata record stored in the logistics operation data store 413, a locationfor the asset to be delivered to. In some embodiments, this changing isbased on data located in the computer-readable indicia.“Computer-readable indicia” as described herein is any tag (e.g., RFIDor NFC tag) information, bar code, data matrix, numbers, lines, shapes,and/or other suitable identifier that is machine-readable (and tend notto be readable by a human) because machines can process the data. Insome embodiments, the computer-readable indicia includes an ID of theasset that the computer-readable indicia is coupled to and the addressor location of the site where the asset is to be returned to (e.g., anaddress of a retailer that sold the item of the asset). This informationmay be contained within the computer-readable indicia even before arequest has been made to return an asset (e.g., as soon as a shippinglabel is placed on an asset by a shipper or carrier personnel) in casethe asset is requested to be returned at some future time. Accordingly,some embodiments automatically replace a destination location or address(e.g., a recipient's address as located in the logistics operation datastore 413) in a data record to the address or location of the site wherethe asset is to be returned to (e.g., third party retailer warehouse).In some embodiments, the return label generator 407 automaticallygenerates a new label by importing or copying information decoded fromthe computer-readable indicia. For example, as described above, theverification module 505 can read the decoded information that indicatesthe address of the return site and responsively generate a new shippinglabel that includes the address of the return site, except that theaddress is in natural language that is human-readable.

In some embodiments, the output of the return label generator 407 isaltered or modified data relative to the previous steps. For example,the output of the return label generator 407 can be structured, tagged,cleaned, and/or otherwise include data in a standardized format (e.g., adigital shipping label), which altogether, is different than data inputby users or the components 401, 403, and/or 405 (which may benon-standardized or unstructured). For example, the output can be afield or standardized data record that includes: the name of therecipient, the address or location (e.g., geo-coordinates) of thefacility to return the asset to, the address or location of the carrierstore facility (or access point) that the recipient will drop the assetoff at, the reasons for requesting a return the asset, a request toprint the generated label, the ID of the asset requested to be returned,and/or a shipping label that contains this information.

In some embodiments, in response to the return label generator 407generating a shipping label to return the asset(s) requested to bereturned, a return label 409 is caused to be printed (e.g., by theprinter(s) 123). For example in some embodiments, in response to thereturn label generator 407 generating a return label, this component canautomatically send a control signal (e.g., via the network 135) to theprinter(s) 123, which causes the printer(s) 123 at a particular carrierstore (e.g., as indicated in the user profile data store 411 and/or thelogistics operation data store 413) or access point (e.g., aparticipating retailer) to automatically print a tangible copy of thegenerated return label 409. In this way, for example, when a recipienttravels to a carrier store (e.g., a store that offers full-servicepackaging and shipping services) or access point, the label may alreadybe printed such that the label can quickly be fixed to the assetrequested for return without carrier personnel having to manually enterthis information after the recipient arrives, which is tedious asdescribed above.

In alternative embodiments, the printer(s) 123 may be located at therecipient's or other user's home, such that a control signal is sent toprint the generated labels 409 so that the recipient or other user canbe the entity to place the return label on the asset that has beenrequested for return. In some embodiments, a control signal need not besent directly to the printer(s) 123. Rather, in some embodiments, beforethe return label 409 is printed, a recipient may take the assetrequested for return to a carrier store or access point. A scanningdevice of the clerk or other carrier personnel may then scan thecomputer-readable indicia (which may have already been scanned by therecipient per the asset return request module 403) located on theoriginal shipping label (which includes the recipient's address or otherdestination location). In response to this scanning device scanning thecomputer-readable indicia, the return label 409 is printed. The clerk orother carrier personnel may then affix the return label 409 over the oldlabel with the original computer-readable indicia still viewable (i.e.,it is not completely covered by the return label 409). In this way, ifthere is another issue with the asset downstream, such as another defectwhen it is ultimately shipped to the recipient again, the same processcan be repeated using the computer-readable indicia. After the clerk orother carrier personnel affixes the return label 409 over the old label,the asset is returned to the address as indicated in the new returnlabel 409.

The notification module 515 is generally responsible for generating andsending notifications to one or more devices indicating that a returnlabel has been generated and/or associated information. For example, thenotification module 515 can transmit, via an email channel (or otherchannel, such as SMS text), a new tracking number for tracking the assetas it gets returned and/or the new asset/item that ultimately getsresent to the recipient. Alternatively or additionally, a proof oftendering notification may be transmitted to a shipper device (e.g., thethird party server(s) 125 or shipper's mobile device) and/or recipientdevice (e.g., computing entity 110) indicating that the asset was indeeddelivered to the recipient notwithstanding the asset was requested forreturn.

FIG. 5 is a block diagram of a system for generating a return labelrequest and a notification, according to some embodiments. Although thesystem 500 includes specific modules or components that operate in aparticular order, it is understood that this is representative only. Assuch, there may be more or fewer components than illustrated, componentsmay be combined, and/or functionality can be performed in a differentorder than illustrated. For example, in some embodiments, the shipperdevice notification module 508 is not present. In some embodiments, eachof the components of the system 500 are located within the one or morecomputing entities 110. Alternatively, in some embodiments, thecomponents of the system 400 are located within a different entity(e.g., third party server(s) 125) and/or are distributed among one ormore components of the environment 100.

The scanning module 502 electronically scans or reads computer-readableindicia located on an asset. A user, such as an asset recipient, maydetermine that he or she will return an asset back to the consignor,shipper, or other location (e.g., an access point). The user may have alocally stored application on his or her mobile device (e.g., a smartphone). In response to opening or selecting the application, the usermay select an electronic scanning feature (e.g., a QR scanner), whichmay responsively activate a camera device or scanner. In response to thecamera or scanner being within a distance, range, and/or viewing frameor capability threshold of the computer-readable indicia, the scanningmodule 502 may automatically capture and decode the computer-readableindicia.

In some embodiments, in response to the scanning module 502electronically scanning or reading the computer-readable indicia, themobile device (or computing entity) that includes the camera device orscanner, automatically sends an asset return request to a computingdevice, which is then automatically received by the asset return requestmodule 403 as described in FIG. 4. Alternatively or additionally, insome embodiments, in response to the scanning module 502 scanning orreading the computer-readable indicia, the computing entity opens (e.g.,automatically or via link that is automatically generated upon a decodeof the computer-readable indicia) the verification interface module 504(e.g., a web or app page) that includes fields or other elementsconfigured to receive authentication and/or authorization informationfrom the recipient. For example, there may be a username and/or passwordfield, a field that prompts the user to input reasons why the recipientwants to return the asset, a field that prompts the user to input a time(e.g., a date/date range) for when the recipient wants the new oracceptable item/asset shipped to her, a field that prompts the user toindicate whether the user will print the label herself and have carrierpersonnel pick the asset up at her place of residence (or otherlocation) or travel to a particular shipping store (and if so, whatspecific asset drop-off location in order to automatically print ashipping label at that location), and/or the like.

In some embodiments, in response to receiving the user input via theverification interface module 504, the computing entity transmits (e.g.,automatically) a return label request via the return label requestmodule 506 (e.g., to the logistics server(s) 105) to request that ashipping label be generated for the return of the asset. In someembodiments, the return label request that is transmitted is received bythe asset return request module 403 as described with respect to FIG. 4,after which the modules 405, 407, and/or 415 may perform theirrespective functionalities.

Additionally or alternatively in some embodiments, in response toreceiving the user input via the verification interface module 504, thecomputing entity transmits (e.g., automatically) a notification via theshipper device notification module 508 (e.g., to the logistics server(s)105) to notify one or more computing devices associated with a shipper(e.g., the mobile computing entity 110 and/or the third party server(s)125) that the recipient has requested that an asset be returned. In someembodiments, this notification can be identical or similar to thenotification sent via the notification module 415 of FIG. 4.

FIG. 6 is a schematic diagram of an environment 600 illustrating how anasset return request may be generated and what a shipping label may looklike, according to some embodiments. The environment 600 includes a user602 (e.g., a recipient) that is holding a mobile device 604, whichelectronically scans or reads the computer-readable indicia 608-1 of theshipping label 608 located on the asset 606. In some embodiments, themobile device 604 represents the computing entity 110 of FIG. 1.

The user 602 may receive the asset 606 from a shipper (e.g., directlyfrom a shipper or via a web application transaction to order anassociated item). The user 602 may then decide that the asset 606 or oneor more items within the asset 606 are not suitable for one or morereasons, such as damage, the wrong item, not enough items, or the like.Accordingly, instead of the user 602 physically travelling to a carrierstore or interfacing with a web application for extensive manual inputto facilitate the return of the asset 606, as is typical andconventional with existing technologies and in the shipping industry, anasset return request may be automatically generated, as well as otherfunctionality described herein, such as with respect to FIGS. 4 and 5.For example, the user may open up or select an app on her mobile device604, which causes a scanner application to activate. The user 602 maythen orient a camera device or scanning device toward the shipping label608 such that the computer-readable indicia 608-1 is in a field of viewof the camera device. In response to the camera device or othercomponent within the mobile device 604 decoding the computer-readableindicia 608-1, a request or notification may be transmitted (e.g.,automatically) to one or more computing devices, which may include arequest to print a return shipping label (or more specifically a portionto replace the natural language section 608-2) of the shipping label 608based on information within the computer-readable indicia 608-1. In someembodiments, this request or notification may be the request and/ornotification as described with respect to the return label requestmodule 506 and/or the shipper device notification module 508.

The shipping label 608 includes a natural language section 608-2 andcomputer-readable indicia 608-1. The natural language section 608-2includes human-readable natural language indicia, such as sender (e.g.,recipient) address information, as well as the address and/or otherlocation (e.g., geo-coordinates) information where the asset 606 isshipped to. Originally, the natural language section 608-2 may includesender address and/or other information of the shipper and an addressand/or other information of the recipient. However, when a return labelis generated and printed (e.g., the return label 409), in someembodiments, the natural language section 608-2 is replaced by a newnatural language section where the sender information now includes therecipient (i.e., because the recipient now want to send the asset back),and/or the “shipped to” or recipient information now includes the siteof return address and/or other location information. And in someembodiments, regardless of this change to the natural language section608-2, the computer-readable indicia 608-2 remains unchanged throughoutall delivery phases. This is because in some embodiments, thecomputer-readable indicia 608-1 always includes the address and/or otherlocation of a site of return for the asset (or items within an asset) incase the asset has to keep being returned for some reason. In someembodiments, the shipping label 608 additionally or alternativelyincludes other information, such as a tracking code (to track an assetas it moves along or within a logistics network or delivery route),delivery service type (e.g., “next day air”), weight of asset, billinginformation, name of item/asset, and/or other computer-readable indicia,such as bar codes and the like.

In some embodiments, information contained in the computer-readableindicia 608-1 is included in the asset return request and is used togenerate a return label. In some embodiments, the computer-readableindicia 608-1 includes the address or location for the site of return(e.g., an address of a retailer warehouse) and/or asset ID. In variousembodiments, in response to this information being scanned by the mobiledevice 604, it is transmitted (e.g., via the return label request moduleand/or the shipper device notification module 508) to one or morecomputing devices so that the new shipping label natural languagesection (similar to 608-2) can be changed and be generated, as describedwith respect to the return shipping label 409, for example.

FIG. 7 is a schematic diagram of an environment 700 illustrating how anasset return request may be generated and an associated user interface,according to some embodiments. The environment 700 includes a user 702(e.g., a recipient) that is holding a mobile device 704, whichelectronically scans or reads the computer-readable indicia of theshipping label 708 located on the asset 706. Subsequent to the scan, theuser interface 720 is displayed. In some embodiments, the mobile device704 represents the computing entity 110 of FIG. 1. In some embodiments,the environment 700 represents the same environment 600 and vice versa,except with the additional functionality associated with the userinterface 720. For example, the user 702 may be the user 602. The mobiledevice 704 may be the same mobile device 604. The asset 706 mayrepresent the asset 606. And the shipping label 708 may represent thesame shipping label 608. In some embodiments, the user interface 720represents or is generated by the verification interface module 505 asdescribed with respect to 504.

In response to the mobile device 704 electronically scanning thecomputer-readable indicia on the shipping label 708, a request may begenerated to return the asset 706. In some embodiments, in response tothe generating this asset return request, the user interface 720 and/orassociated web or app pages are automatically displayed (e.g., by theverification interface module 504). For example, an authentication pagemay first be rendered which prompts the user 702 to input his/herusername and/or password and responsively the user interface 720 isrendered (e.g., because the verification module 405 has verified thatthe mobile device 704/user 702 is located within the user profile datastore 411). Alternatively or additionally, in some embodiments the userinterface 720 and/or associated authentication/authorization pages arerendered manually on the mobile device 704. For example, once the user702 determines that she wants to return the asset 706, he or she maymanually select an app or navigate to a web page that includes the userinterface 720. In some embodiments, the application that activates thecamera/scanner as described with respect to the mobile device 604 is thesame application responsible for rendering the user interface 720 (e.g.,the scanning module 502 and verification interface module 504 areincluded in the same application). In other embodiments, these areseparate applications stored to the mobile device 704.

The user interface 720 is configured to receive user input for changingand address location and/or generating a new shipping label, accordingto particular embodiments. Although the user interface 720 representsspecific elements, features, buttons, menus, with a particular look andfeel, it is understood that this is representative only and that anyparticular element, feature, button, menu, and look and feel may existor replace the illustrated features. Moreover, more features may beadded or removed. For example, there may not be a prompt that requeststhe user 702 to input where the user 702 will drop off the item.

The buttons 720-1 are selectable by the user 702 to ensure the user 702indeed wishes to return the asset 706. The field 720-1 is configured toreceive natural language input by the user 702, such that the user canspecify why the user 702 wishes to return the asset 702. For example,the user 702 can indicate that an item is: damaged, is the wrong item ordifferent than the item ordered, an attribute of the item (e.g., color,size, etc.) is incorrect or different than the attribute selected, theuser 702 is not happy with the item, and/or the like. In someembodiments, instead providing a field 720-2 that receives naturallanguage input, the user interface 720 may provide a menu or otherelement of pre-determined options for the reasons of return.

The menu selections 720-3 are selectable by the user 702 as options forwhere the user 702 will drop off the asset 706 to facilitate its return.The user 702 may select, for example to drop off the asset 706 at anearby shipping store. In some embodiments, in response to thisselection, one or more Application Programming Interfaces (API)corresponding to a map (e.g., GOOGLE maps) of different carrier storescan be displayed and the user 702 can select which store that she willdrop the asset 706 off at. The user 702 may alternatively select, forexample, to drop off the asset 706 at a participating access point(e.g., a retailer). In some embodiments, in response to this selection,one or more APIs corresponding to a map of different access points canbe displayed and the user 702 can select which access point that shewill drop the asset 706 off at. The user 702 may alternatively select,for example, an option to just have the asset 706 picked up from herplace (e.g., place of residence, geo-coordinates, or employer address).In response to this selection, some embodiments provide a notificationto the mobile device 704 that asks whether the user 702 would like toprint his or her own new shipping label so that the new shipping label(with the new return facility address) is already affixed to the asset706 when carrier personnel pick it up. In some embodiments, each ofthese selections indicated in the menu 720-3 are used by embodiments toperform specific printing or changing of record functionality, asdescribed in more detail below.

Some or each of the information inputted or selected by the user 702within the user interface 720 may be included in an asset return requestas described herein. In some embodiments, some or all of the informationinput to the user interface 720 (and/or authentication information) isobtained by the return label request module 506 and/or shipper devicenotification module 508 and transmitted to the asset return requestmodule 403 of FIG. 4 or other component so as to facilitate thegenerating of a return shipping label or change an address that theasset 706 gets shipped to, as described, for example, with respect tothe modules 405, 407, and 515 of FIG. 4. In some embodiments, some orall of the information input by the user 702 to the user interface 720is obtained at registration time or is located within the user profiledata store 411 such that one or more portions of the user interface 720does not need to be provided. Rather, automatic requests can begenerated without user input.

In some embodiments, some or all of the user input that is provided tothe user interface 720 is used to generate a return shipping label orchange the shipping address. In this way, the changing of the address orgeneration of the shipping label can be based at least in part on theinput provided to the user interface 720 by the user 702. For example,in response to the user 702 selecting an option to return the asset 706to “a nearby shipping store,” and selecting a specific location, thereturn label request module 506 can receive this information andtransmit an asset return request (e.g., to the logistics serer(s) 105),which gets routed to the specific location that the user 702 selectedfor drop off. This asset return request may act as a control signal(e.g., to the printer device(s) 123) or notification for the specificlocation to print the new shipping label (e.g., as described withrespect to the shipping label 608 of FIG. 6). This functionality maysimilarly occur when the user 702 selects the “a participating accesspoint” option. In another example, in response to the user 702 selectingan option to “just pick it up at my place,” the return label requestmodule 506 can receive this information and transmit (e.g.,automatically) a control signal to a printer device (e.g., which mayhave an IP address or other registered information indicated in the userprofile data store 411) within the user's 702 dwelling or otherlocation. Alternatively, for example, carrier personnel devices (e.g.,DIADs) may receive indications of the “just pick it up at my place”option and responsively generate and/or print a new return label suchthat when the asset is picked up, carrier personnel can place thealready-printed new return label on the asset to facilitate its return.

IV. Exemplary System Operation

FIG. 8 is a flow diagram of an example process 800 for automaticallychanging a destination location for one or more assets to be deliveredto for the generating of a return label, according to some embodiments.The process 800 (and/or any of the functionality described herein, suchas process 900) may be performed by processing logic that compriseshardware (e.g., circuitry, dedicated logic, programmable logic,microcode, etc.), software (e.g., instructions run on a processor toperform hardware simulation), firmware, or a combination thereof.Although particular blocks described in this disclosure are referencedin a particular order at a particular quantity, it is understood thatany block may occur substantially parallel with or before or after anyother block. Further, more (or fewer) blocks may exist than illustrated.For example, in some embodiments, the process 800 may not include theblock 808, which may be optional. Any added blocks may include blocksthat embody any functionality described herein. The computer-implementedmethod, the system (that includes at least one computing device havingat least one processor and at least one computer readable storagemedium), and/or the computer program product/computer storage media asdescribed herein may perform or be caused to perform the process 800,and/or any other functionality described herein. In some embodiments,the logistics server(s) 105 performs the process 800. Alternatively,some or all of the components of FIG. 1 performs the process 800.

Per block 802, one or more identifiers (associated withcomputer-readable indicia that is electronically scanned) is received.For example, at a first time, one or more identifiers are received basedon an electronic scan of computer-readable indicia. The “identifiers” asdescribed herein may be the computer-readable indicia itself,computer-readable indicia that has been decoded (e.g., natural languagewords or character sequences that represent the computer-readableindicia), a flag, and/or a notification that computer-readable indiciahas been scanned. In another example, at a first time, an indication maybe received that computer-readable indicia is electronically scanned. Inlike manner, the “indication” as described herein may be thecomputer-readable indicia itself, computer-readable indicia that hasbeen decoded (e.g., natural language words or character sequences thatrepresent the computer-readable indicia), a flag, and/or a notificationthat computer-readable indicia has been scanned. In some embodiments,the computer-readable indicia is coupled (e.g., adhesively fixed) to oneor more assets. In some embodiments, the asset is associated with one ormore shipping operations.

In other words, some embodiments receive at a first time, an indicationthat computer-readable indicia is electronically scanned by a computingdevice, the computer-readable indicia being coupled to an asset, whereinthe asset is caused to be shipped by a shipping entity and delivered toa destination location associated with a recipient of the asset. A“shipping entity” as described herein refers to a consignor, a shipper(e.g., a retailer that sells an item to be delivered to a destinationlocation), or a logistics company/carrier (e.g., UPS).

A “shipping operation” as described herein is any suitable operationrelated to shipping, such as a final mile delivery of assets (i.e.,delivering assets to final destination location), delivering assets fromone sorting facility to another, delivering assets from a carrier storeto a sorting facility, importing or exporting assets, flying orotherwise carrying assets to/away from a sorting facility, loading anasset into a logistics vehicle, picking an asset from a logisticsvehicle for drop off at another location, etc. An “asset” as describedherein is any tangible item that is transported from one location toanother. Assets may be or include the contents that enclose product orother items people wish to ship. For example, an asset may be or includea parcel or group of parcels, a package or group of packages, a box, acrate, a drum, a container, a box strapped to a pallet, a bag of smallitems, and/or the like.

In some embodiments, block 802 is performed by the asset return requestmodule 403 of FIG. 4 and/or performs any functionality as described withrespect to the return request module 403 of FIG. 4. In an illustrativeexample of block 802 and referring back to FIG. 6, the logisticsserver(s) 105 or other component may receive the identifiers orindications that the mobile device 604 has electronically scanned thecomputer-readable indicia 608-1. In some embodiments, thecomputer-readable indicia includes a matrix barcode such that a mobiledevice associated with the recipient scans the matrix barcode prior tothe receiving of the indication. A “matrix barcode” as described hereinis a two-dimensional symbology that encodes text, numbers, files, or anysuitable data (e.g., cells, boxes, lines, etc.). For example, the matrixbarcode may be a QR code, a data matrix, a PDF417, an Aztec code, Code39, MAXICODE, or the like. In some embodiments, the mobile devicescanning and related functionality is described with respect to FIG. 6.

In some embodiments, the computer-readable indicia includes an ID of theasset(s) it is coupled to and a site location (e.g., physical address orgeo-coordinates, such as longitude and latitude) for the return of theasset(s), which may be used to perform block 806, as described in moredetail below.

Per block 804, it is determined that one or more assets have beenrequested for return. For example, in some embodiments, based at leastin part on the receiving of the indication (that computer-readableindicia is electronically scanned), it is determined that a recipient ofthe corresponding asset has requested a return of the asset. In anotherexample, based at least in part on the one or more identifiers (that arereceived per block 802), that is determined that an asset is requestedfor return. For example, based on analyzing the content of the decodedcomputer-readable indicia (e.g., address of return facility),embodiments can determine that a user or recipient has requested areturn of an asset. In some embodiments, block 804 occurs“automatically” (e.g., as a background task without an explicit userselection or input). Examples of block 804 are described with respect tothe asset return request module 403 and FIGS. 6 and 7.

In some embodiments, in response to the receiving of the indication (asdescribed with respect to block 802), a web page or app page isautomatically caused to be displayed to a user device. In someembodiments, the web page or app page is indicative of authenticatingand authorizing the recipient to return the asset. For example, such webpage or app page may be or include the user interface 720 as describedwith respect to FIG. 7. In some embodiments, the web page or app page isadditionally or alternatively indicative of information provided tousers in order to help facilitate block 806 and/or block 808. Forexample, referring back to FIG. 7, the input that is provided via themenu 720-3 can be used by embodiments to facilitate the generating of ashipping label as described with respect to FIG. 7.

In some embodiments, in response to the receiving of the one or moreidentifiers (described at block 802), embodiments automaticallyauthenticate and authorize a recipient for the return of an asset. Forexample, instead of a user having to manually enter in authentication(e.g., a password) information to the user interface 720, embodimentscan automatically authorize the return of the asset (e.g., viainformation located in the user profile data store 411, as opposed toinformation still needing to be input at the user interface 720). Insome embodiments, the automatic authentication and authorization isbased on contents of the computer-readable indicia, such as the new siteof return address, and the like.

Per block 806, based at least in part on content of thecomputer-readable indicia, a destination location for the asset(s) to bedelivered to is automatically changed. For example, based at least inpart on contents within the computer-readable indicia, a location forthe asset to be delivered to is automatically changed in a structureddata record stored in computer memory. A “structured data record” asdescribed herein is any suitable structured object, such as a databaserow or record, field, entry, or other data store record that is storedin computer memory (e.g., RAM or non-volatile storage hard drives).Referring back to FIG. 4, for example, the return label generator 407can change a record located in the logistics operation data store 413,as described above. The “content” of the computer-readable indicia mayinclude the asset(s) ID, the address or other location of the facilitythat accepts returns, and/or any other suitable data, such as newtimeline for shipping the corresponding new item. Accordingly, the“destination location” is no longer the original recipient's address orlocation but is the address or location that accepts the returndelivery.

In some embodiments, the one or more identifiers (described at block802) or the computer-readable indicia include an ID of the asset and asite location for the return of the asset such that the changing atblock 806 includes changing a first address to a second addresscorresponding to the site location based reading the computer-readableindicia. Examples of this (and block 806 in general) are also describeabove with respect to the shipping label 608 of FIG. 6, where anoriginal recipient address can be changed (e.g., on the natural languesection 608-2) to a return site address that is included in thecomputer-readable indicia 608-1.

Per block 808, a return shipping label is generated (e.g., as describedwith respect to the return label generator 407). Some embodimentsautomatically generate a shipping label in response to the automaticallychanging as described with respect to block 806 and the return labelgenerator 407. Based at least in part on the one or more identifiers (orcontents of the identifiers descried at block 802), some embodimentsautomatically generate a shipping label corresponding to a destinationlocation for the asset to be returned to (e.g., as described withrespect to the return label generator 407). Some embodimentsadditionally or alternatively cause a tangible printing of the shippinglabel (e.g., as described by the return label 409 of FIG. 4) in responseto the generating of the shipping label at block 808. For example,referring back to FIG. 1, the logistics server(s) 105 (or mobilecomputing entity 110) can send a control signal to the printer device(s)123 to print a paper copy of a shipping label. In another example, the“causing” a tangible printing may alternatively not include a controlsignal, but a notification that a return label is ready to be printed.Accordingly, for example, in response to carrier personnel scanning thecomputer-readable indicia, carrier personnel can manually print out thenew return label.

Some embodiments receive, at a second time subsequent to the first time(described at block 802), a second indication that the computer-readableindicia has been scanned. In some embodiments, the scanning of thecomputer-readable indicia at the second time is at least partiallyindicative of the asset being located at a shipping facility that printslabels. For example after the mobile device 604 has scanned thecomputer-readable indicia 608-1 as illustrated in FIG. 6, the user 602may travel to a logistics store to drop the asset off. Subsequently, aclerk or carrier personnel located at the logistics store may use ascanner to scan the computer-readable indicia as described with respectto FIG. 4. In some embodiments, in response to the receiving of thesecond indication, embodiments automatically cause a printing of ashipping label (e.g., the generated shipping label at block 808) at theshipping facility or logistics store so that the shipping label can beaffixed to the asset(s) to facilitate the return of the asset(s), asdescribed for example with respect to FIG. 4. For example, after theclerk or other carrier personnel uses a scanner to scan the asset(s),embodiments automatically send a control signal to a printer in thefacility or notification to the carrier personnel such that the returnshipping label is printed. Subsequently, the carrier personnel can affixthe new return shipping label to the returned asset for return.

In some embodiments, prior to the automatically generating of theshipping label (block 808), embodiments change a structured data recordcorresponding to a destination location for the asset to be shipped tobased on location information (e.g., address or coordinates for the siteof return) included in the one or more identifiers, as described, forexample, with respect to block 806 and/or the return label generator407.

In some embodiments, there are other operations or blocks notillustrated in the process 800 that can occur, such as a tangibleprinting of the generated return shipping label. For example, someembodiments cause a tangible printing of the shipping label in responseto the generating of the shipping label based at least in part onsending a control signal to a printing machine (e.g., the printingdevice(s) 123 of FIG. 1) in a logistics facility (e.g., carrier store,logistics store, or any suitable location that facilitates delivery ofassets). Some embodiments receive an indication that thecomputer-readable indicia is scanned at a logistics store or accesspoint and in response to the receiving of this indication, embodimentsautomatically cause (e.g., via a control signal or notification asdescribed above) a printing of a shipping label where the shipping labelis to be affixed to the asset to facilitate the return of the asset.

FIG. 9 is a flow diagram of an example process 900 for generating one ormore notifications that include a request to return one or more assets,according to some embodiments. In some embodiments, the process 900 isperformed by the computing entity 110 of FIG. 1. Alternatively oradditionally, in some embodiments, some or each of the blocks areperformed by other components of FIG. 1. In some embodiments, more orfewer blocks can be included in the process 900. For example, in someembodiments, the process 900 does not include block 903 such that thenotification(s) are generated in response to block 901. Any

Per block 901, embodiments scan computer-readable indicia coupled to oneor more assets. In some embodiments, this may include electronicallyscanning, by a mobile device, computer-readable indicia that is coupledto an asset where the asset is associated with one or more shippingoperations. For example, the mobile device 604 can scan thecomputer-readable indicia 608-1 of FIG. 6. In an illustrative example ofblock 901, the scanning module 502 as described with respect to FIG. 5can scan computer-readable indicia. In some embodiments, thecomputer-readable indicia includes a matrix barcode such that a mobiledevice recipient of the asset scans the matrix barcode such that inresponse to the mobile device scanning the matrix barcode, the receivingof the one or more identifiers occurs (e.g., as described at block 802of FIG. 8).

Per block 903, one or more portions of a user interface to verify one ormore users are generated. For example, at least partially in response tothe electronically scanning at block 901, embodiments generate (e.g.,automatically) one or more portions (e.g., a window, a notification, abutton, a page) of a user interface. In some embodiments, the one ormore portions are indicative of a prompt for a user to inputverification information for a return of the asset. A “prompt” asdescribed herein is a request, field, button, feature, element, or anysuitable notification that is provided to a user device so that the userdevice can input information. In some embodiments, the prompt includes arequest for the user to input authentication information. In anillustrative example of block 903, an interface may be generated by theverification interface module 504 as described with respect to FIG. 5,for example. In another example, the user interface 720 (or any portionthereof) can be generated as described with respect to FIG. 7.

Per block 905, particular embodiments generate one or more notificationsthat include a request to return the one or more assets. In someembodiments, the one or more notifications include a messagestransmitted to a logistics server associated with a logistics facilityto automatically print a shipping label for the asset. For example, thisnotification may include a notification as received or transmitted bythe return label request module 506 to the asset return request module403. In this example, this notification is transmitted to the assetreturn request module 403 and subsequently processed by the components405, 407, 415 as described with respect to FIG. 4). In some embodiments,the one or more notifications include a message transmitted to a userdevice (or other computer, such as the third party server(s) 125)associated with a shipper of the asset and the message includes anindication that the asset is requested to be returned to the shipper.For example, this notification may include a notification as received ortransmitted by the shipper device notification module 508 as describedwith respect to FIG. 5. In another example, the indication can benatural language text transmitted to a shipper user device thatindicates that the recipient is returning one or more assets back to theshipper because of particular reasons.

In some embodiments, a mobile device or other user device associatedwith a recipient generates a shipping label (e.g., at least partially inresponse to the receiving the input of the verification information).For example, referring back to FIG. 7, in response to the userpopulating the fields and other features within the user interface 720,embodiments can generate a new shipping label with an address of thephysical site of return (e.g., as indicated in the computer-readableindicia). In some embodiments, the mobile device or other user devicecause a tangible printing of the shipping label (e.g., in response tothe generating of the shipping label). For example, a user device of arecipient can send a control signal to a printing machine located in heror her home, which prints (e.g., automatically) the generated shippinglabel.

Definitions

“And/or” is the inclusive disjunction, also known as the logicaldisjunction and commonly known as the “inclusive or.” For example, thephrase “A, B, and/or C,” means that at least one of A or B or C is true;and “A, B, and/or C” is only false if each of A and B and C is false.

A “set of” items means there exists one or more items; there must existat least one item, but there can also be two, three, or more items. A“subset of” items means there exists one or more items within a groupingof items that contain a common characteristic.

A “plurality of” items means there exists more than one item; there mustexist at least two items, but there can also be three, four, or moreitems.

“Includes” and any variants (e.g., including, include, etc.) means,unless explicitly noted otherwise, “includes, but is not necessarilylimited to.”

A “user” or a “subscriber” includes, but is not necessarily limited to:(i) a single individual human; (ii) an artificial intelligence entitywith sufficient intelligence to act in the place of a single individualhuman or more than one human; (iii) a business entity for which actionsare being taken by a single individual human or more than one human;and/or (iv) a combination of any one or more related “users” or“subscribers” acting as a single “user” or “subscriber.”

The terms “receive,” “provide,” “send,” “input,” “output,” and “report”should not be taken to indicate or imply, unless otherwise explicitlyspecified: (i) any particular degree of directness with respect to therelationship between an object and a subject; and/or (ii) a presence orabsence of a set of intermediate components, intermediate actions,and/or things interposed between an object and a subject.

The terms first (e.g., first request), second (e.g., second request),etc. are not to be construed as denoting or implying order or timesequences unless expressly indicated otherwise. Rather, they are to beconstrued as distinguishing two or more elements. In some embodiments,the two or more elements, although distinguishable, have the samemakeup. For example, a first memory and a second memory may indeed betwo separate memories but they both may be RAM devices that have thesame storage capacity (e.g., 4 GB).

The term “causing” or “cause” means that one or more systems (e.g.,computing devices) and/or components (e.g., processors) may in inisolation or in combination with other systems and/or components bringabout or help bring about a particular result or effect. For example,the logistics server(s) 105 may “cause” a message to be displayed to acomputing entity 110 (e.g., via transmitting a message to the userdevice) and/or the same computing entity 110 may “cause” the samemessage to be displayed (e.g., via a processor that executesinstructions and data in a display memory of the user device).Accordingly, one or both systems may in isolation or together “cause”the effect of displaying a message.

The term “real time” includes any time frame of sufficiently shortduration as to provide reasonable response time for informationprocessing as described. Additionally, the term “real time” includeswhat is commonly termed “near real time,” generally any time frame ofsufficiently short duration as to provide reasonable response time foron-demand information processing as described (e.g., within a portion ofa second or within a few seconds). These terms, while difficult toprecisely define, are well understood by those skilled in the art.

The term “coupled” to refers to two or more components being attached,fixed, or otherwise connected. Any suitable component can be used tocouple components together, such as one or more: screws, bolts, nuts,hook fasteners, nails, etc.

The following embodiments represent exemplary aspects of conceptscontemplated herein. Any one of the following embodiments may becombined in a multiple dependent manner to depend from one or more otherclauses. Further, any combination of dependent embodiments (e.g.,clauses that explicitly depend from a previous clause) may be combinedwhile staying within the scope of aspects contemplated herein. Thefollowing clauses are exemplary in nature and are not limiting:

What is claimed is:
 1. A computer-implemented method comprising:receiving, at a first time, an indication that computer-readable indiciais electronically scanned by a computing device, the computer-readableindicia being coupled to an asset, wherein the asset is caused to beshipped by a shipping entity and delivered to a destination locationassociated with a recipient of the asset; at least partially in responseto the receiving of the indication, determining that the asset isrequested to be returned back to the shipping entity; and based at leastin part on content of the computer-readable indicia, automaticallychanging, in a structured data record stored in computer memory, thedestination location to a return location associated with the shippingentity.
 2. The method of claim 1, further comprising automaticallygenerating a shipping label in response to the automatically changing.3. The method of claim 2, further comprising causing a tangible printingof the shipping label in response to the generating of the shippinglabel.
 4. The method of claim 1, wherein the computer-readable indiciaincludes a matrix barcode, and wherein a mobile device associated withthe recipient scans the matrix barcode prior to the receiving of theindication.
 5. The method of claim 1, wherein the computer-readableindicia includes an ID of the asset and a site location for the returnof the asset, and wherein the changing includes changing a first addressto a second address corresponding to the site location based on readingthe computer-readable indicia.
 6. The method of claim 1, the methodfurther comprising: in response to the receiving of the indication,automatically causing a web page or app page to be displayed to a userdevice, wherein the web page or the app page is indicativeauthenticating and authorizing the recipient to return the asset.
 7. Themethod of claim 1, further comprising: receiving, at a second timesubsequent to the first time, a second indication that thecomputer-readable indicia has been scanned, the scanning of thecomputer-readable indicia at the second time is at least partiallyindicative of the asset being located at a shipping facility that printslabels; and in response to the receiving of the second indication,automatically causing a printing of a shipping label at the shippingfacility, wherein the shipping label is to be affixed to the asset tofacilitate the return of the asset.
 8. A system comprising: one or moreprocessors; and one or more computer storage media storingcomputer-useable instructions that, when used by the one or moreprocessors, causes the one or more processors to perform a method, themethod comprising: receiving, at a first time, one or more identifiersbased on an electronic scan of computer-readable indicia, thecomputer-readable indicia being coupled to an asset, the asset isassociated with one or more shipping operations; based at least in parton the one or more identifiers, determining that the asset is requestedfor return; and based at least in part on the one or more identifiers,automatically generating a shipping label corresponding to a destinationlocation for the asset to be returned to.
 9. The system of claim 8, themethod further comprising changing, prior to the automaticallygenerating of the shipping label and in computer memory, a structureddata record corresponding to a destination location for the asset to beshipped to based on location information included in the one or moreidentifiers.
 10. The system of claim 9, the method further comprisingcausing a tangible printing of the shipping label in response to thegenerating of the shipping label based at least in part on sending acontrol signal to a printing machine in a logistics facility.
 11. Thesystem of claim 8, wherein the computer-readable indicia includes amatrix barcode, and wherein a mobile device of a recipient of the assetscans the matrix barcode, and wherein in response to the mobile devicescanning the matrix barcode, the receiving of the one or moreidentifiers occurs.
 12. The system of claim 8, wherein the one or moreidentifiers includes an ID of the asset and a site location for thereturn of the asset, and wherein the changing includes changing a firstaddress to a second address corresponding to the site location based onreading the computer-readable indicia.
 13. The system of claim 8, themethod further comprising in response to the receiving of the one ormore identifiers, automatically authenticating and authorizing arecipient for the return of the asset.
 14. The system of claim 8, themethod further comprising: receiving and indication that thecomputer-readable indicia has been scanned at a logistics store oraccess point; and in response to the receiving of the indication,automatically causing a printing of a shipping label, wherein theshipping label is to be affixed to the asset to facilitate the return ofthe asset.
 15. A computer storage media having computer-executableinstructions embodied thereon that, when executed, by a processor,causes the processor to perform a method, the method comprising:electronically scanning, by a mobile device, computer-readable indiciathat is coupled to an asset, the asset is associated with one or moreshipping operations; at least partially in response to theelectronically scanning, generating, by the mobile device, one or moreportions of a user interface, the one or more portions are indicative ofa prompt for a user to input verification information for a return ofthe asset; and based at least in part on the generating of the one ormore portions, generating, by the mobile device, a notification thatincludes a request to return the asset.
 16. The computer storage mediaof claim 15, the method further comprising generating, by the mobiledevice, a shipping label at least partially in response to receiving theinput of the verification information.
 17. The computer storage media ofclaim 16, further comprising causing, by the mobile device, a tangibleprinting of the shipping label in response to the generating of theshipping label.
 18. The computer storage media of claim 15, wherein thenotification includes a message transmitted to a user device associatedwith a shipper of the asset, wherein the message includes an indicationthat the asset is requested to be returned to the shipper.
 19. Thecomputer storage media of claim 15, wherein the notification includes amessage transmitted to a logistics server associated with a logisticsfacility to automatically print a shipping label for the asset.
 20. Thecomputer storage media of claim 15, wherein the prompt includes arequest for the user to input authentication information.